Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Warmers: Dedicated Norms/Terms warm options in mappings #4079

Closed
kimchy opened this issue Nov 4, 2013 · 1 comment
Closed

Warmers: Dedicated Norms/Terms warm options in mappings #4079

kimchy opened this issue Nov 4, 2013 · 1 comment
Assignees
@jpountz
Labels
>enhancement v0.90.10 v1.0.0.RC1

Comments

@kimchy
Copy link
Member

kimchy commented Nov 4, 2013

Similar to the loading part in fielddata, where someone can configure if they are loaded eagerly or not, we should have the same option in mappings for norms, and for terms.

Idea regarding naming, within a field:

{
   "terms" : {"loading" : "lazy|eager"},
    "norms" : {"enabled" : false|true, "loading" : "lazy|eager"}
}

Note, the above will deprecate the omit_norms field mapping, and follows similar structure to the fileddata mapping config.
@s1monw
Copy link
Contributor

s1monw commented Nov 13, 2013

moved over to 0.90.8

@ghost ghost assigned jpountz Dec 20, 2013
jpountz added a commit to jpountz/elasticsearch that referenced this issue Dec 27, 2013
@jpountz
Eager norms loading options.
cb5803d 
Norms can be eagerly loaded on a per-field basis by setting norms.loading to
`eager` instead of the default `lazy`:

```
"my_string_field" : {
  "type": "string",
  "norms": {
    "loading": "eager"
  }
}
```

In case this behavior should be applied to all fields, it is possible to change
the default value by setting `index.norms.loading` to `eager`.

Close elastic#4079
@jpountz jpountz mentioned this issue Dec 27, 2013
Closed
@jpountz jpountz closed this as completed in 9763d07 Jan 6, 2014
jpountz added a commit that referenced this issue Jan 6, 2014
@jpountz
Eager norms loading options.
dbe7f82 
Norms can be eagerly loaded on a per-field basis by setting norms.loading to
`eager` instead of the default `lazy`:

```
"my_string_field" : {
  "type": "string",
  "norms": {
    "loading": "eager"
  }
}
```

In case this behavior should be applied to all fields, it is possible to change
the default value by setting `index.norms.loading` to `eager`.

Close #4079
brusic pushed a commit to brusic/elasticsearch that referenced this issue Jan 19, 2014
@jpountz @brusic
Eager norms loading options.
032f285 
Norms can be eagerly loaded on a per-field basis by setting norms.loading to
`eager` instead of the default `lazy`:

```
"my_string_field" : {
  "type": "string",
  "norms": {
    "loading": "eager"
  }
}
```

In case this behavior should be applied to all fields, it is possible to change
the default value by setting `index.norms.loading` to `eager`.

Close elastic#4079
@johtani johtani mentioned this issue Jan 28, 2014
Merged
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@jpountz
Eager norms loading options.
2514d9d 
Norms can be eagerly loaded on a per-field basis by setting norms.loading to
`eager` instead of the default `lazy`:

```
"my_string_field" : {
  "type": "string",
  "norms": {
    "loading": "eager"
  }
}
```

In case this behavior should be applied to all fields, it is possible to change
the default value by setting `index.norms.loading` to `eager`.

Close elastic#4079
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jpountz jpountz

Labels
>enhancement v0.90.10 v1.0.0.RC1
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Eager norms loading options. jpountz/elasticsearch
3 participants
@kimchy @jpountz @s1monw